Shareware Super Platinum 8

home *** CD-ROM | disk | FTP | other *** search

/ Shareware Super Platinum 8 / Shareware Super Platinum 8.iso / mac / EDITORS / BIBNT310.ZIP;1 / BIBLNET.DOC < prev next >

Wrap

Text File | 1993-01-18 | 54.7 KB | 1,229 lines

BIBL/NET [NetWare] release 3.10 (c) 1992,93 Clyde W. Grotophorst GMUtant Software Route 1, Box 296 Hamilton, Virginia 22068 U.S.A. BIBL/NET features include: - full NOVELL locking supported. Advanced routines enable BIBL to avoid record-locking (which has a serious impact on network performance) and yet provide complete database integrity. - support for up to 50 simultaneous users (100 user version available) - six levels of security ensure database integrity and protect files from unwanted modification. BIBL/NET automatically defaults to READ-ONLY access if a user is not in the BIBL security database--making it easy to offer BIBL/NET to most users. - multiple databases are supported. Users with level 3 or greater security may create and maintain PERSONAL databases...inaccessible to other users. - REGISTERED VERSION only. BIBL/NET picks up the user login name from NetWare (if in the BIBL/NET security database, user need only enter password -- simplifying login) - mouse-support - easily understood user interface (bounce-bar menus or first letter of each command). - four indexes are maintained (in a single file) for fast retrieval and sorted extracts (author, author/title, title, and descriptor). - up to 9 words from the keyword field are indexed individually. - each user has a system record which stores his 'home' directory (for export and storage of PRIVATE databases). - produces bibliographies in several forms (brief, annotated, full (and with registered version labelled), full) based on information in any field. Each bibliography is sorted by author, then within author, by title. - when no match is made on an indexed search, BIBL/NET displays where in the index your query would have appeared (near misses). - produces a wide variety of lists (in ASCII form) which may be printed or edited with any word-processor that accepts ASCII files for input (most do). - an ASCII file viewer that supports a mouse, and is moveable, resizeable, and ZOOMable. File viewer points automatically to users 'local' directory--the same place BIBL/NET export files (reports) are routed. - ability to print or save to disk any individual record. - main menu screen always reports active database, security level of user, and number of records in the file. - verification of keywords during data entry (if desired) - Boolean AND, OR, NOT searching supported for ALL fields. Up to four terms may be used. May also limit search to descriptor field. - Selected reports (list of subjects, list of titles, etc) may be viewed onscreen and/or sent to disk. - BIBL/NET can produce a comma-delimited file of the database. - any ASCII file may be used for display when I (INFORMATION) is pressed on the main menu. - Shell to DOS (heap compression frees additional memory) - Global Find & Replace for text in ANY field, across a database. - BIBL/NET will run in 43/50 line mode. INSTALLATION Installing BIBL/NET on your network is relatively simple. Follow these three steps: NOTE! Be sure to assign user names that are IDENTICAL to the user name used by NOVELL. BIBL/NET will carry the NOVELL username into the security routine and check the BIBL/NET security database (BIBLSEC.DAT) for that name. If a user in BIBLSEC.DAT has a different user name than the NOVELL login name, then no match will be possible and the user will have ONLY read access to the system. 1. On your local machine (not necessarily on the net) run BNETSEC.EXE to create the security database (BIBLSEC.DAT and BIBLSEC.IX) BIBL uses. When finished, move BIBLSEC. DAT and BIBLSEC.IX to the public (applications) directory where you will be running BIBLNET.EXE. IMPORTANT! Flag both BIBLSEC.DAT and BIBLSEC.IX as RWSH (read/write share hidden). Netware Command: FLAG BIBLSEC.* RWSH [return] This will allow BIBL/NET to find them but hides them from your users. Note that the information in BIBLSEC.DAT is encrypted...to aid in maintaining security. ONLY code within BIBLNET (the program) and BIBLSEC (the security maintenance utility) will enable you to 'see' what's in the security database. For this, and other obvious reasons, don't put BNETSEC.EXE in your public directory--otherwise users will have access to your security. You can run BNETSEC from your local hard disk and point it to your network database area via the BNETSEC command line (e.g., BNETSEC y:\apps\gmutant). 2. Copy BIBLNET.EXE and BIBLNET.HLP to the public (applications) directory where you just put BIBLSEC.DAT and BIBLSEC.IX. Flag both files ROS (read only share). You can flag BIBLNET.HLP as ROSH (read only share hidden) if you wish. If you want to install the demonstration database, copy DEMO.DAT and DEMO.IX to that directory as well. Flag those files RWS (Read-Write, SHARE). Users must have read/write/create access in the BIBL/NET subdirectory! 3. Log onto the network and type BIBLNET to activate the program. Enter your user name (you assigned it during your initial session with BNETSEC.EXE), then your password. You will then be given access to the program. Here's how BIBL/NET is run on our Novell 2.20 (50 user) Lan: First, BIBLNET.EXE BNETSEC.DAT BNETSEC.IX and BIBLNET.HLP all reside in a public applications directory named Y:\APPS\GMUTANT. Next, each user is mapped to a home directory (in our case H:) that looks to the user like a root H: drive. This is where all their personal files for Quattro Pro, BIBL/NET and other shared applications reside. It is this drive that we enter for each user in the BNETSEC.DAT security database (Export Path). Since each user is mapped there as a ROOT drive, all that needs to be entered in the BIBL/NET security database is H:\. Finally, our NOVELL menu program contains a BIBL/NET option which, when selected, runs this BATCH file: @Echo off Y: cd\apps\gmutant BIBLNET cd\apps H: This changes the directory to where BIBLNET resides (Y:\APPS\GMUTANT) so that directory will be the default when BIBL/NET activates--important since we have to be able to find BNETSEC.DAT and the databases. When the program exits, it sets the drive back to H: BIBL/NET SECURITY When a user signs onto the BIBL/NET system, he must provide a UserName (which you assign) and a password. Based on this information, BIBL/NET checks the security database and assigns the user a security level (0 - 5). The security level of the user determines what sorts of things he can do within the program. LEVEL 0: A user with Security Level 0 receives READ-ONLY access to BIBL/NET databases. No export is allowed. This might be the security level for GUEST users... Note that you don't really need an entry in your security file for LEVEL 0 users...that's the default. LEVEL 1: Similar to level 0, although user is allowed to export data from public databases to his local workstation. LEVEL 2: User may add records but has no edit or delete capability. LEVEL 3: User may add records. User may also edit and/or delete any records he or she has created, but not records created by others. This is probably your most common security level--at least for users you want to have adding records... but unable to delete records added by others. Users at Level 3 and above may also create personal (private) databases that are stored in their Export path (as defined via BNETSEC). Level 3 and above users can create/delete private databases, run global change on private databases, and run ascii import. LEVEL 4: User may add, edit or delete *any* records in *any* public database. LEVEL 5: All rights. This user may also create and/or delete databases and may initiate index rebuilding and ASCII (BIX file) import. You should not have too many LEVEL 5 users since some activities able to be performed by this level user will have a dramatic impact on BIBL/NET's performance for other users (e.g., importing ASCII (BIX) files). For each user, beyond assigning a user name (12 characters max), a password (11 characters max) and a security level (1-5), you may also indicate a subdirectory on their local machine where exported information (reports, individual record dumps, etc) may be directed. The individual user may modify either his password or this Local Export path at any time from the BIBL/NET maintenance menu. Additionally, you must assign a 3 letter code for each user (typically their initials). This code is 'STAMPED' in each record that individual creates on the system. It is this code that BIBL/NET checks (along with the user's security level) to determine who may delete and/or edit the record. You might consider using letters that don't typically occur in words... in that way, you can find all the records 'owned' by a given user by searching the code under FULL SEARCH. Typical entry in the security database: UserName: WALLYG Password: MRWALDO UserStamp: CWG <- all records created by user get this SecurityLevel: 3 ExportPath: H:\BIBL\ <- this is where private databases reside * IMPORTANT * After building your initial security database (BIBLSEC.DAT and BIBLSEC.IX), move both files to the network drive where BIBLNET.EXE resides and flag both files (BIBLSEC.DAT and BIBLSEC.IX) as HIDDEN, READ/WRITE. The data in the file is encrypted so users can't download the datafile and deduce passwords; however, if you don't HIDE the files, BIBLSEC.DAT will show up as a database under BIBL and cause a trashed display for the user who selects it! Adding more users at a later date To add additional users at any time, run BNETSEC and point it to your production security database on the network drive. This is done via the command line (e.g., BNETSEC Y:\APPS\GMUTANT). BNETSEC implements file locking to enable you to modify the database--even if a user is simultaneously updating his or her record (password or export directory). SYSTEM OVERVIEW BIBL (rhymes with nibble) /NET is a simple to use, networked online catalog for your personal and/or business library. Written in Borland Pascal 7.0 and using full B-tree indexing (thanks to TurboPower's B-Tree Filer package), the system is fast, small, and very efficient. Menu-driven, BIBL/NET can be used to track your book collection, article reprints, index your vertical file, manage a small office library, and so on... In most areas bounce-bar menus are used. To select a particular option, move the bar via the cursor until your desired operation is highlighted, then press RETURN. If you're a touch typist, you might prefer pressing the highlighted letter within (or just to the left of) the choice you wish to make (e.g., Press S to activate SEARCH on the main menu). On single line menus (e.g., when displaying matches), you may hit the highlighted letter to execute the command, or move between them via the TAB key. Clicking a mouse on your menu choice will also activate it. Command Line Switches ( /m or /v ) If on a monochrome monitor you find you can not clearly read the various BIBL/NET status line displays, activate program with an '/m' switch (for mono), e.g., BIBLNET /M <cr>. You may use any combination of command line arguments, in any order--with the exception that FILENAME if it appears must be the first one. BIBL/NET will also run in 43 or 50 line mode (EGA or VGA) if you start the program with a /v switch. BIBL/NET will automatically detect hardware and make the appropriate setting. MAIN MENU OPTIONS Security Option Level Description 0-5 L List items in the database. This option allows you to move through the database a record at a time. The records appear in the order in which they were entered into the system. Pressing L on the main menu takes you to the last record in the file (the assumption being that you are probably more interested in the more recent records). You may move about the file via the J (Jump) command--which 'jumps' you to the record number you enter. If user has a security level of 2 or below, the edit and delete options are disabled. At level 3, options are enabled if user created the records (record contains his 3 letter User Stamp). 0-5 S Search a database. Supports a variety of search types. 1-5 E Export data. Enables user to produce a variety of reports. 1-5 V View ASCII file(s). Allows user to look at an ASCII file. If you are using the registered version, and have installed a word processing program (e.g., WordPerfect) as your external editor/viewer, then pressing V calls that program and passes the name of the file to view. 2-5 M Maintenance functions. This function provides a variety of support operations (adding records, rebuilding indexes, creating new databases, deleting databases, Shell to DOS, etc). The number of options displayed depends on the user's security level. 0-5 D Database selection. Once you have created a second database, this function allows you to move between database files. 0-5 I Information on BIBL/NET. Pressing I on the Main Menu causes the file BIBLNET.HLP to display in a window on your screen. To create your own help file, make an ASCII file and name it BIBLNET.HLP. You do not have to worry about page breaks or other formatting. 0-5 Q Quit to DOS. Closes all files, halts program and exits. DATABASES BIBL/NET can manage up to 400 distinct databases. While the structure of each database is the same, you may have several--enabling you to separate out records that belong together. Each 'database' consists of two files (*.DAT and *.IX). You create empty databases from the Maintenance sub-menu. Once created, you may select (or activate) a particular database via the Database Selection option on the main menu. SEARCHING THE DATABASE To search, press S at the main menu, then via the light bar select which field you wish to search (Author, Title, Subject, etc.). Once you have selected the field you wish to search, a 'QUERY' box will appear. Enter the text you wish to locate in this box, at the 'Query >>' prompt. You may search text in ANY field of a BIBL/NET record. Matches are made using your input as a stem; that is, if you enter SMI and SMITH exists, you'll get a match (it's called implied truncation). Note that while retrieval on indexed fields is very fast, searching non-indexed fields (e.g., line 3 of the note field) is much slower. On non-indexed fields, BIBL/NET must read each record, comparing your query with the contents of the field. You may abort a non-indexed search by pressing any key to interrupt. On indexed field searches, if BIBL/NET can not find a match for your query, it will display several index entries that come before and after where your query would have fallen in the index. As your database grows, this becomes more useful. If you want to abandon searching after you have selected a particular field to search, press RETURN instead of entering a search statement at the 'Query >>' prompt. You will be returned to the main menu. BOOLEAN SEARCHING (AND / OR / NOT) Use BOOLEAN search to search for up to 4 terms in a record. You may search either the full record or limit the search to the descriptor field. BOOLEAN searching does not use an index, so retrieval time is a bit longer. When the full record is searched, a high speed search algorithm (Boyer-Moore) is employed--this yields a significant performance improvement over searching just the Descriptor field--where BIBL/NET uses a more traditional approach (reading each record and comparing the field to your input). You may select either BIX format (for subsequent transfer to another database) or plain ASCII (no labels, formatted like QUERY.TXT entries). You give BIBL/NET a name for the output file and based on your format choice, the extension (BIX or TXT) is automatically appended. EDITING/DELETING RECORDS IN THE DATABASE You may enter EDIT mode either via a search or by the LIST function (press E when the desired record displays. You may well find editing via LIST more efficient (since BIBL/NET does not return you to the search menu after a change is made). As you first enter EDIT mode, the author's name field will be highlighted. Make any changes you desire, using the cursor arrow keys to move between fields. When you have finished making changes, press ESC (or RETURN if line 7 of the note field is highlighted). You will receive an 'OK to file (y/n)?' prompt. Respond with: Y - The index will be updated if editing changed an indexed field. N - Changes will be discarded. The original record redisplays. You may also enter EDIT mode via the 'List records in the database' option from the main menu. The only difference between editing from this menu choice instead of SEARCH is that BIBL will display all records in the database, beginning with the last record. With the 'Jump' command, you may find this method of editing superior to that offered during a search--you don't exit the loop after performing an edit. MAINTENANCE MENU The MAINTENANCE menu appears with level 2 or greater security. It offers several options (the specific ones offered are determined dynamically based on a user's security level): - Add Records to the Database (level 2 or greater) - Rebuild Index for active database (level 5 only) - Shell to DOS (level 2 or greater) - Make a new database (level 4 or greater) - Delete a database (level 4 or greater - Import a BIX (ASCII) file (level 4 or greater) - Global Find / Replace (level 4 or greater) - Network Information (level 2 or greater) - Change User Password/Export Directory (level 2 or greater) - Zap (delete) a BIX file (level 3 or greater) - Quit to Main Menu ADDING RECORDS TO A DATABASE Each database is limited to 2 billion records although you'll run out of disk space long before that becomes an issue. To begin working toward that 2 billion, press A as the main menu displays. A blank record appears on the screen. Enter data in the highlighted fields. If you want to skip a field, just press RETURN when the cursor is inside that field's highlighted box. When you are finished, either press return when the highlighted box is in line 10 of the note field, or press ESC. BIBL/NET will then offer a prompt line at the bottom of the screen, asking to file the record, continue editing, verify keywords or abandon it. You may click the appropriate response with your mouse or enter the highlighted first letter of the option you desire (e.g., A to Abandon). You may verify that the descriptors you're using for a new record conform to those already in your database. Just hold the ALT key down and press V. BIBL/NET will check the terms in the field against the database, putting a check mark by each that is found. BIBL/NET INDEXING Four indexes are maintained in the single file: 1) the first 15 characters of the author field, 15 characters of the TITLE field, each word (something with a space before and after it) of the DESCRIPTOR field (must be more than a single character), and a fifth index for author/title sorting. By putting all five indexes in a single file, performance is improved over systems that put each index in its own file--DOS does not allocate a large number of file handles for BIBL's use. Information is stored in upper case in the index file and your query is converted to upper case before a search begins--thus you don't have to worry about capitalization (although the way you enter data is the way it will display and appear in any ASCII file created by BIBL/NET). Note: If your database is large (5000 records or more) and your network is under a heavy load, you can dramatically improve reindexing times by moving your database to a local workstation and reindexing it under a copy of BIBLNET.EXE running on the local workstation. You'll need to move BIBLSEC.DAT and BIBLSEC.IX to that local workstation and have IPX and NETX loaded for BIBLNET to run. When finished, copy the *.DAT and *.IX files back to your server. FIELDS (Subject vs Keyword) Most fields are obvious, but you might not be familiar with the distinction we're making between subject and keywords. Put the most important term in the subject field and other less useful but desired descriptive terms in the Keys: field. EVERY word (anything between spaces) in the keyword field is individually indexed. Caution: No term in the keyword field can be longer than 20 characters (or it will be truncated to 20 characters in the index). The indexing algorithm considers a word to be anything between two blank spaces. If you have a compound term, include a '-' between the words so they'll be considered a single term (e.g., 'World-War-II' is considered 1 term while 'World War II' is three.). Up to 9 words in any one KEYS field will be indexed. A single letter WILL NOT be indexed. Each 'word' must be longer than one character. LOCATION: You may use the location field for either a classification number (if your organization system is that evolved) or simply where you have stored the physical item referenced in the BIBL/NET record. REBUILDING INDEXES BIBL includes an index rebuild function to create new indexes from the database file on demand. You may never need this function, but if add records through the ASCII import function; take a power hit during data entry, or experience some other sort of hardware (disk) failure, the index can become invalid or corrupted. If your database becomes completely corrupted, use BRX to rebuild and repair it. Rebuilding indexes will correct any problems of this sort. When rebuilding the indexes, BIBL provides a graph which shows the status of the effort (0%-100% complete for each index). If you have fewer than 50 records, the blocks in the graph represent each record. SHELL TO DOS BIBL allows you to drop out of the program momentarily and return to your DOS prompt. This option allows you to delete files, use a program like LIST to view a file, check disk space, or do other DOS-type things. BIBL provides a special prompt to remind you to enter EXIT to return to the program. When you type EXIT, BIBL will reactivate and check to see that the operating system is still defaulting to the sub-directory where your BIBL files are kept. If not, BIBL will change to that drive and directory before continuing. If BIBL is unable to change to the original sub-directory, you will receive a message to that effect...so you can manually issue the command (e.g., CD\BIBL <cr>) from the DOS prompt. MAKE A NEW DATABASE. To create a new, empty database, press M on the maintenance menu, then enter a name for the database file. You may enter up to 8 letters for your database name. You should try to give the file a name that will later give some indication of the file's contents. TIP: When creating databases, give your most popular file a name that sorts first. The Database Selection option on the main menu sorts the various *.DAT files before displaying them. The first file in the list will be highlighted when the list displays. If it is the file you want, just press RETURN (or ESC). Note that you can also specify a database on the command line when activating BIBL from the DOS prompt (e.g., BIBL Myfile). DELETE A DATABASE. You may use this function to delete a database and it's associated index file. You may also delete a database and index by simple using the DOS delete command while at the DOS prompt. BIBL dynamically determines your databases by scanning the directory where BIBL.EXE resides for files ending with the *.DAT extension. You may NOT DELETE the database you are currently using. IMPORT a BIX (ASCII) FILE Using the ASCII import option enables you to read any labelled ASCII file into the currently active BIBL database. The file separated with **'s and each line is labelled. The labelled option under the Export Menu creates this format as does the Transfer option when displaying an individual record. If you want to experiment with ASCII import (say you're trying to import an ASCII file from some other source--like bibliographic data downloaded from a CD-ROM), you should follow these steps: 1. Use MAKE A NEW DATABASE option on maintenance menu to create a database called something like TEST 2. Use DATABASE SELECTION on the main menu to select the TEST database. 3. Run ASCII import from the maintenance menu. You BIX file must be in the same subdirectory where BIBL.EXE resides. 4. After reviewing the results (the records added to TEST), select the database you want to use and run ASCII import again. When finished, you can delete TEST.DAT and TEST.IX via Delete a Database (on the maintenance submenu). GLOBAL FIND/REPLACE Global changes ('find & replace') affect any record across your database. To make a global find and replacement, select the field you want to modify (the database will be the currently active file--the database that displays on the status bar at the bottom of your screen). After selecting the field to modify, you must next enter the original text (what's currently in the record(s)) and then the new text. In both situations (the finding and the replacing) the case of the text you enter is significant and your 'find' input must match the database EXACTLY. Be advised that the substitution you instruct BIBL to make will occur anywhere BIBL finds a match for your 'change' text. Without a bit of thought on your part, this can quickly become a nightmare. If you elect to change a short word--one that also appears as part of a larger word in the same field--you can have problems. For example, asking BIBL to change NETWORK to LAN can (if you also have NETWORKING in the same field) lead rather quickly to LANING... You are not limited to whole word changes (if the text you enter happens to match a few letters inside another word in that field, it will be changed. Again, think your change through before you begin. It is possible that the length of your replacement term(s) will force the truncation of the field. For example, if your descriptor field has 60 characters and you change one 5 letter word to a 15 letter word, the field would now be 75 characters long...so the last 5 characters of your field after the 5 letter word becomes a 15 letter one will be chopped off. NETWORK INFORMATION Selecting N on the Maintenance menu brings up a screen of information about your network. BIBL/NET will attempt to tell you: the interface card in the server version of NETWARE in use maximum number of connections supported number of connections in use current broadcast status free RAM in the workstation and so on. CHANGE USER PASSWORD / EXPORT DIRECTORY This option allows the user to change his password and the path (drive and subdirectory) where BIBL points the file viewer, writes export files, and transferred or saved records. BIBL/NET will place the '\' at the end of the path name if it is not added by the user. If the export field is blanked out, BIBL/NET will not allow export. EXPORT MENU While BIBL/NET offers only limited print support, it will dump your database to disk in an ASCII file--which you can then edit and print using your favorite word processor. Blank fields do not appear in the ASCII files BIBL creates. (the exception being DELIMITED format). You may select Author, Title, Subject, Delimited or the order records appear in the database. Note that each time you call the dump to disk routine it overwrites any previously created file. Here is a list of the files created via the Export function. Where you are given the option of naming the file, you should use a *.TXT extension when possible. This will allow you to see all available export files under the VIEW function when you accept the default *.TXT mask. BIBL/NET writes export files to the user's Export Directory (typically one on their local machine). BIBL can create ASCII files (full, annotated or brief form) for all records that contain your search string. Annotated form will produce a listing with author, title, publisher and the notes fields. Brief includes only the author, title, and publisher field. Below, a sample 'annotated' reference appears: Bratley, Paul and Choueka, Yaacov Processing Truncated Terms in Document Retrieval Systems. Information Processing and Management v18 n5 p257-66 1982 Presents uniform and efficient approach for processing all truncated query terms in information retrieval which requires one disk access to obtain from the permuted dictionary all strings represented by truncated term. The problem of the overhead storage required to implement the permuted dictionary is discussed. Fifteen references. You assign the name for the bibliography output file. If the name is already in use, BIBL asks you to use another name. Note that using the Word Processing [WP] format option will produce a citation where fields follow one another on a line. A hard return follows the PUBL field. Bratley, Paul and Choueka, Yaacov. Processing Truncated Terms in Document Retrieval Systems. Information Processing and Management. v18 n5 p257-66. 1982. 'Smart' Punctuation [WP format] As BIBL creates your bibliography, it will check to see if each field ends with punctuation. If so, the existing punctuation will be written to your file. If not, BIBL will add periods after each field. This saves you having to use end-of-field punctuation in your BIBL database entry. DELIMITED FORMAT Delimited format is used when you want to move your BIBL database to dBASE or some other database system (why?). The next few paragraphs point out a few things you should be aware of: Note that in delimited format BIBL will change any quotation mark that appears in the Title, Descriptor, or Note fields to a single quote--to preserve the exported data's integrity. If any double quotes were to appear in the exported data (that is, anywhere other than between the fields), the importing program might not process the data correctly. For example, if you have: Jones is author of the article, "This is My Life's Work." in your note field, under delimited format, BIBL will export: "Jones is author of the article, 'This is My Life's Work.'" A CR/LF appears at the end of each record. dBASE will accept this for input if you first set up a dBASE file with the proper structure. Use the field lengths as they appear at the end of this documentation. With the database structure created, activate dBASE and issue the following command: . USE MYBOOKS <cr> . APPEND FROM BIBLDLM.TXT DELIM <cr> LIST SUBJECTS/LIST DESCRIPTORS (Keywords) You should use these export functions periodically to check the uniformity of your subject headings and descriptor fields. For example, if your list shows you have 10 items under computer and 1 under computers, you should edit the COMPUTERS entry (changing it to COMPUTER). As an aid in helping you identify the records, a bit of the title is included with each entry. Note that there is an entry in the list for each heading in a record (if you have 10 records with the subject BASEBALL, you'll get 10 entries for BASEBALL in the SUBRIEF.TXT file). KEYWORD.TXT - this option lists all terms used in the descriptor field of your database. With each term, the number of times it appears is also listed. This list can be a big help in eliminating redundant terms and consolidating similar terms to yield a stronger database. Related Topics Send To Disk. Beyond creating large reports, during any search you may elect to send a copy of a single record to an ASCII file (QUERY.TXT). Each time you press 'S' a copy is appended to this file. When you are finished with the file, delete it (via DOS) or rename it. Then when you next send a record to disk, BIBL will create a new copy of QUERY.TXT. Transfer: Any time an individual record is displayed, you have the option of copying it to a transfer file (TRANSFER.BIX). Pressing T (or clicking on the word 'Transfer' will add the record to TRANSFER.BIX. To move the records in TRANSFER.BIX use ASCII import on the maintenance menu. Be sure to delete any existing TRANSFER.BIX file if you want to make a file of new records...if TRANSFER.BIX exists on your disk, transferred records will be appended to it. If it is missing when 'T' is pressed, BIBL will create USAGE NOTES / TIPS A. Here are some of the ways we've heard BIBL is being used: - as an online index to a personal book collection. - tracking magazine articles. - indexing a vertical file (for non-library types, a vertical file is usually a filing cabinet of clippings, brochures, etc.). - using BIBL instead of 3x5 cards for research. - tracking reserve reading materials in a corporate library. - Managing an office library. B. Modifying HELP display (INFORMATION on the main menu). BIBL displays the file BIBLNET.HLP when 'I' is pressed on the Main Menu. If you want to change the help display file, just rename any ASCII file to BIBLNET.HLP and BIBL will display it... Technical Specs: 1. Memory required. BIBL requires a minimum of 435K RAM to operate. If you have more, then more will be available when you Shell to DOS. PASCAL structure for a BIBL/NET record: bookrec = RECORD recordstatus : longint; { deleted?} linkfile : string[30]; {reserved} value : string[6]; author1 : string[70]; author2 : string[70]; Title1 : string[70]; title2 : STRING[70]; title3 : string[70]; publ : STRING[70]; publ2 : string[70]; class : STRING[40]; subject1 : string[30]; subject2 : STRING[70]; flag1 : char; {user stamp in these 3 char fields} flag2 : char; flag3 : char; createdate : string[7]; note1 : STRING[70]; note2 : STRING[70]; note3 : STRING[70]; note4 : STRING[70]; note5 : STRING[70]; note6 : STRING[70]; note7 : string[70]; note8 : string[70]; note9 : string[70]; note10 : string[70]; end; Indexes (the following keys are maintained in each .IX file): Author first 15 characters of the field (stored upper case) Title first 15 characters of the field (stored upper case) Author/Title 14 characters of author+6 characters of title. Keyword first each word of the field is extracted (a word being a string of characters separated by a space or comma). Up to 20 characters of each 'word' is indexed. Up to 9 words from any one line are indexed. If you have 10 words on the line, the tenth is ignored. IMPORTANT: place a '-' between words you want BIBL/NET to index together. File extensions used by BIBL/NET .DAT - a datafile .IX - the index to a DAT datafile. .DIA - dialog file used by BIBLNET.EXE to handle locking. .HLP - Help file (displays when I is pressed on Main Menu) .SAV - temporary file, used during index rebuild/purge. The *.DAT and *.IX files together form 'a database.' You must have the same name on both you .DAT and .IX files--usually taken care of by BIBL but if you rename a database via DOS (for example, renaming DEMO.DAT to MYFILE.DAT, be sure to rename DEMO.IX to MYFILE.IX too!). .TXT - any ASCII file. .BIX - BIBL Import/Export. A labelled ASCII file. This file uses a specific format where each field is labelled (e.g., A1:, A2: for the 2 author fields, T1: T2: T3: for the title fields, and so on. Each record in the file is separated by '**'. The ASCII import function on the Maintenance Menu will read a BIX file and write the information to BIBL records. You can use this facility for backing up your database or moving records from one database to another. Here is a sample record in BIX format: ** A1: Bratley, Paul and Choueka, Yaacov T1: Processing Truncated Terms in Document Retrieval Systems. PB: Information Processing and Management. Volume 18, Number 5 P2: pages 276-66. 1982 SU: Information Retrieval VL: 9.95 DE: Information-Storage Permuted-Indexes Subject-Indexing N1: Presents uniform and efficient approach for processing all N2: query terms in information retrieval which requires one disk N3: access to obtain from the permuted dictionary all strings N4: represented by the truncated term. The problem of the N5: overhead storage required to implement the permuted N6: dictionary is discussed. Fifteen references N7: are provided. ** Note: BIBLNET.EXE has been compressed with PKLITE version 1.15 Databases created by the single user version of BIBL or the unregistered (SHAREWARE) version of BIBL/NET are fully compatible with the registered version of BIBL/NET. If moving a database created by the single-user version of BIBL to the network for use by BIBL/NET, you have to be sure the DAT and IX and DIA files are flagged RWS (Read Write Sharable). You must also rebuild the index under BIBL/NET as the author/title index is built on the fly during reports in the single user version. Security file used by unregistered version (BIBLSEC.DAT and BIBLSEC.IX) is the same used by the registered version of BIBL/NET. Upgrading from shareware to registered is a quick, and painless process. Basically, you just replace the BIBLNET.EXE file with its registered counterpart. You must have the IPX and NETX drivers loaded to run BIBL/NET Questions, comments, complaints, encouragement??? Contact: Clyde W. Grotophorst, Route 1, Box 296, Hamilton, VA 22068 voice: (703) 993-2239 or call the GMUtant OnLine BBS (703) 993-2219, and leave a comment for the Sysop. The Bulletin Board is your source for updates and additional BIBL/NET utilities. You may also reach the author via Compuserve (70404,3376). Notes: Appendix A. A BIBL record defaults to the following field labels (not all the note field is shown for brevity sake): Auth: : Title: : : Publ: : Locn: Date: Subj: Value: Desc: Note: : It is possible to modify these labels on the record display screen, the data entry screen and the edit screen. To do so, you must create an ASCII file similar to the one shown below. In the sample below, we want to modify the Location field (uses the label Locn: in the above example) to show Class: (as in classification). First, with an ASCII editor create a file with the same filename as the database you want to perform this modification on...but give the file a DBL extension. For example, say you wanted to modify the DEMO.DAT database that comes with BIBL, you'd create a file named DEMO.DBL Using the convention established with BIX files (where each field is labelled), you'd enter the following line in the file: CL=Class: CLMENU=Call Nmbr The CL= line governs what label BIBL will use for that field when displaying a record. The CLMENU= line governs how BIBL/NET will refer to the field on the SEARCH and EXPORT menu screens. Limitations: The label text can be no more than 6 characters. The menu text can not exceed 9 characters. Any field you do not modify in your *.DBL file will retain the BIBL/NET default value. Here's a complete sample file for a database that's being used not as a book catalog but as a faculty directory: A1= Name: A2=Phone: T1=Membr: PB= Dept: P2= Schl: CL= Rank: SU=Rsrch: DE= Desc: N1= Note: VL= Cost: AUMENU=Professor TIMENU=Membrship PBMENU=Affiliate SUMENU=Research CLMENU=Rank With these 13 lines (and yes, each entry must occupy a single line and begin in the first position of the left margin), we change the look of this one database...all other BIBL/NET databases (unless they too have a corresponding DBL file) will use the BIBL/NET book-oriented defaults. Any BIBL/NET field label can be modified. Five fields may be renamed throughout the program: Author, Title, Publisher, Location and Subject. When you delete a database that has an associated DBL file, BIBL will ask if you want that label file removed as well. Leaving it causes no problems other than consuming a few hundred bytes of disk space. You may use WordPerfect to create a label configuration file but be sure to save the file using CTRL-F5 (text out). If you want a database to revert to the original default labels and field names, just delete the associated *.DBL file for that database. ** IMPORTANT ** The operation of the program is not changed by these modifications. If, for example, you do as we've shown in the sample above and divide the author field into 2 fields (one for name and one for phone), BIBL will still treat them as an entity when producing reports -- which in this case would concatenate (or join) them. Finally, when assigning values to AUMENU, TIMENU, CLMENU and SUMENU, be sure that you *DO NOT* have the same letter beginning more than one values--or use the same first letter as is used by one of the fields that you can not change (e.g., D for Descriptor). In several instances during operation, BIBL will accept the initial letter of the strings you assign as the hot key. If two begin with the same letter, pressing that letter will always activate the first term (for example, don't have AUMENU=Editor and SUMENU=Edition -- both begin with an E). Appendix B. Value field BIBL/NET will now track a value for each item in a database. The value field is limited to 6 spaces (so you can store between 0 - 999.99 for a given item). Should you have an item worth more than 999.99 you can omit the decimal and track values up to 999999. When BIBL computes the total value for a database, it will treat 999999 as 999999.00. (if you have items worth more than $ 9999999.00 you should probably be using a more expensive solution than BIBL/NET...) The value field label may be changed (using VL= in the *.DBL file). Value appears only in the BIX file (label VL=) and can be read into a BIBL/NET record when using ASCII import. Do not include a $ in your value for an item (e.g., don't enter $ 5.00 -- use 5.00 instead). BIBL/NET will replace any $'s found with 0's. Appendix C. Editing keystrokes supported (use during ADD and/or EDIT): If you know WordStar (or use one of the Borland editors), you'll find most of BIBL's edit commands perform as you'd expect (^ = Control key): ^F or CTRL -> word right ^S - character left ^A or CTRL <- word left ^D - character right ^T - delete word right ^Y - delete line ^E - up one line ^X - down a line ^H - backspace If you're using a mouse, you can click on a field to highlight it for subsequent editing. REVISION HISTORY of BIBL/NET (since 2.50) 3.00 New database structure. BIBL 8.0 and BIBL/NET 3.0 now share same structure...databases may be moved freely between systems (although single-user and network version of BIBL use a different indexing algorithm). Rebuild your index when moving a *.DAT and *.IX file from one version of the program to another! Added mouse support to note field editing. Added ability to move cursor to a specific spot in a record by clicking twice on the spot...a big help for making subsequent edits. Additional RAM freed during Shell to DOS. Will use XMS memory if available at the workstation. Previously, BIBL/NET would use EMS if found but could not manage XMS swapping. Order now is 1) EMS if available, if not, then 2) XMS, if that's not found (or not in sufficient supply), then 3) virtual memory (disk) is used. Expanded "white space" on data entry / edit screen. More room between fields...making it a bit easier to move about (particularly with a mouse). New internal file viewer added. This one can look at files of any size. You probably won't have need for it, but this viewer also supports HEX viewing (just press ALT-H). Press F1 for help with commands when using the built-in viewer. Up to 1000 matches now possible (previously, the system would gather up to 800 matches before display). Due to memory savings realized elsewhere, we've increased this limit to 1000. Changed indexing structure and number of indexed fields...to improve performance and reduce disk space requirements. Now BIBL/NET maintains 4 indexes instead of 5. Gone is the subject index. It wasn't used for much, and was taking 30+ bytes per record. Removing it will speed up redindexing, import, and global changes. While the index for the subject field has been removed, you can still search by subject. See BIBLNET.DOC for complete information on which fields are indexed. Improved support for renamed fields on search screen (popup window where query is entered). 2.70 Introduced CLONING during data entry. If you finish entering a new record and want to copy it to yet another new record (in instances where you have two to enter that differ only slightly), you can press C to Clone the data...then edit the changes in the new record. This is similar to the "carry forward" feature in dBASE. 2.62 Changed name of help info from BIBL.HLP to BIBLNET.HLP. "Show close matches" function (activated when you don't get a match on an indexed search, reworked. Speed increased and disk accesses reduced. 2.61 Fixed a few quirks in User-Selects export option (particularly formats C and E). BIBL/NET now returns to the path where BIBLNET.EXE resides before exiting. Before, if a user was using a PRIVATE database, BIBL/NET would exit back to the private directory when the program was terminated. Verify keys/subject window reworked a bit. 2.60 Now User-Selects export option offers ability to select the order in which fields will appear in reports. New option for output format (tabs between fields and a hard return after each record). 2.57 Under export, BIBL/NET now correctly limits user to entering just a file name for the export file it will create. The Export Path defined in the User's security record will be added so that files are directed to that user's private area (either on the server or their local disk). New option added user export--User Defined. You can now say what fields to include in a report and sort on one of 3 fields (author, title or subject). Option C will output each record on a single line (with a hard return between records). This should be very helpful for word processing. 2.56 Message appears as BIBL/NET is filing a record after an edit. After watching this process on a huge database (and a very slow network), we realized a status message would be helpful 2.55 BIBL/NET now rereads record from disk once "edit" option is selected. This was done to help user learn quickly whether or not a record was deleted between the time it was first displayed and then later selected for editing (pressing E when record was displayed). If a given field in a record is empty, the field label doesn't display. This helps keep the screen from looking too busy on records where only a few fields are used. If file is locked when you select it from the DATABASE selection menu, you'll be returned to the selection menu instead of being dropped back to the DOS prompt. You can now change the display label for DESCRIPTOR field as well. Descriptor is now called Keywords, the default label is 'Keys:' Cleaned up support for field relabelling during global change function. BIBL/NET was reporting default field names, not the ones you might reassign. Everything worked fine but the onscreen information was confusing. 2.54 Added 'Automatic' switch to global find & replace. After reviewing a couple of changes (to insure that BIBL/NET is changing what you expected to be changed) you can press A for AUTOMATIC. The system will automatically make any remaining changes without pausing for your review. SHELL to DOS now frees up more memory. BIX file creation now goes to USER'S PRIVATE DIRECTORY under all conditions. You can not write it to the directory where BIBLNET.EXE resides. 2.53 Several fixes to BIBL/NET operations 2.52 Reworked the way BIBL/NET displays records under indexed searching (author, title, subject and or descriptor). Now BIBL/NET collects all matches and displays them as a set. You can move freely about the set (by pressing F (forward), B (back) or J (jump to a particular record). As a result of this implementation, BIBL/NET is limited to displaying the first 650 matches for a given search. 2.51 Fixed incomplete implementation of label changing via a DBL file. Now search menu and export menu reflect changes made in a DBL file. 2.50 Improved searching algorithm for non-indexed searches. Major reworking of PUBLISHER, LOCATION, FULL and BOOLEAN search function (all non-indexed searches). Gone are the klunky "End of File Reached" messages and the blinking 'wait' as BIBL searched...